home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
wcht201.zip
/
WILDCHAT.DOC
< prev
next >
Wrap
Text File
|
1992-07-10
|
13KB
|
383 lines
┬┬ ┬ ┬ ┬┬ ┬┬─ ─┬┬──┐ ┌┬──┐ ┬┬ ┬ ┌┬──┐ ┌─┬┬─┐ (tm)
││ │ │ ││ ││ ││ │ ││ ││ │ ││ │ ││
││ │ │ ││ ││ ││ │ ││ │├──┤ │├──┤ ││
││ │ │ ││ ││ ││ │ ││ ││ │ ││ │ ││
└┴─┴─┘ ┴┴ ┴┴──┘ ─┴┴──┘ └┴──┘ ┴┴ ┴ ┴┴ ┴ ┴┴
Version 2.01
Tim Rider
4129 Konya Dr.
Torrance, CA 90503
The Source BBS (310) 371-3737
WildChat(tm) is supplied as is. The author disclaims all
warranties, expressed or implied, including, without
limitation, the warranties of merchantability and of
fitness for any purpose. The author assumes no
liability for damages, direct or consequential,
which may result from the use, or inability to use,
WildChat(tm).
(C) Copyright 1992, Tim Rider
What is WildChat(tm)?
═════════════════════
WildChat is a multi-line chat door for the WildCat BBS system. It is
designed to replace the internal multi-line chat by using a DOS Hook
from the main menu.
WildChat(tm) requires BRUN45.EXE, which is not included in this
archive.
Why use it?
═══════════
WildChat is much faster, and provides many more features than
WildCat's internal multi-line chat. WildChat is easier to use,
and basically, a lot more fun.
How does it work?
═════════════════
WildChat uses the disk to store the messages that users type. A
RAM disk is recommended, but not necessary. A disk cache is
necessary only if a RAM disk is not used, but still recommended.
WildChat writes to a fixed length file it creates when it is first
run. This file is called WILDCHAT.MSG, and it contains the messages
that users send to each other. The reason this file is fixed length
is once again speed.
WildChat writes to another fixed length file called WILDCHAT.DTA. This
file contains node info data. This file is used along with WildCat's
own NODEINFO.DAT to keep track of users on the BBS and in the
multi-line chat.
Other features
══════════════
Whispering
──────────
Whispering is one of those handy features that WildCat's multi-line
chat just doesn't have. Normally, messages you type in the multi-
line chat can be seen by everyone. WildChat will let you "whisper"
something to a user privately, so no one else can see your message.
Let me show you an example. Let's say there are two users in the
multi-line chat, T.Rider, and C.North. You are seeing what T.Rider
types.
/C.North No one else can see this message!
C.North would see something like this on his screen...
T.Rider (Whispered): No one else can see this message!
It's a handy feature, a must for any conversation!
Language Filter
───────────────
Naturally, there are always those people who take a liking to words
that you may not want on your BBS. If you BBS is a family system,
then you surely won't want profanity used in the multi-line chat.
The language filter will screen messages for those words which you
specify in the file WILDCHAT.BAT. Read on for more details.
Action Commands
───────────────
Action Commands are another of the great features of WildChat that
WildCat's internal multi-line chat doesn't have. Action Commands
are key-words that are linked to a phrase. I'll give you an
example, since it is kind of hard to explain. Once again, T.Rider
and C.North are in the multi-line chat. We see what T.Rider
types...
LAUGH C.North
Everyone in the chat door would see this...
T.Rider is laughing at C.North!
Or this...
LAUGH
And they would see...
T.Rider is laughing out loud!
instead of seeing "T.Rider: LAUGH C.North". This adds a lot of
realism to the multi-line chat, and is another must have feature.
Read on for more details on how to add and edit action commands.
Help Screens
────────────
WildChat uses two external help screens, they are:
CFGHELP.BBS
MAINHELP.BBS
Of course, example screens have been included, but they aren't very
good, and I hope to improve them some time. Feel free to edit these
screens to your liking.
Files In This Archive
═════════════════════
Make sure that you have all of these files, and that they are the
proper file sizes, etc...
WILDCHAT BAD 50 07-10-92 10:00p
CFGHELP BBS 3891 07-10-92 10:00p
MAINHELP BBS 3525 07-10-92 10:00p
WILDCHAT CFG 2519 07-10-92 10:00p
WILDCHAT DAT 18060 07-10-92 10:00p
WILDCHAT EXE 42907 07-10-92 10:00p
WILDCHAT LST 927 07-10-92 10:00p
Installation
════════════
Make sure ALL nodes are taken down, and that the system is not running
under a multi-tasker before starting this set up. Also, ALWAYS BACK
YOUR SYSTEM UP!
1. Make a sub-directory off of the WildCat root directory for WildChat.
EXAMPLE: C:\WC30\WILDCHAT\
2. Move WILDCHAT.EXE, WILDCHAT.DAT, WILDCHAT.BAD, WILDCHAT.LST into
this directory.
3. Add a command into your CONFIG.SYS or your AUTOEXEC.BAT to create a
128k RAM Disk on bootup.
4. Edit WILDCHAT.CFG. Instructions are in the file, and DO NOT remove
any lines from the file, or your system may suffer a severe disaster.
5. Move the edited WILDCHAT.CFG into the WildCat ROOT directory.
EXAMPLE: C:\WC30\
6. Find a free Main Menu DOS Hook.
7. Create a batch file to call WildChat.
EXAMPLE C:\WC30\MAIN1.BAT (For DOS Hook 1)
@ECHO OFF
C:\WC30\WILDCHAT\WILDCHAT.EXE
8. If your system uses non-standard IRQ or addresses for COM ports,
then make sure to add the proper environment variables to the
correct CATx.BAT file. Variables needed are listed below...
COMBASE This is the base address of the COM port being used.
WCIRQID This is the IRQ of the COM port being used.
WCHOME This is the WildCat home directory.
EXAMPLE SET COMBASE=1016
SET WCIRQID=4
SET WCHOME=C:\WC30\
NOTE: COMBASE *MUST* be in decimal. "03F8" won't work! You
need to use the decimal value, "1016".
9. Use MAKEWILD and do the following...
(a) Change the MAIN MENU "Multi-User Chat" command letter to
something like "!" or "@", so no one can accidently access
WildCat's internal chat.
(b) Change the MAIN MENU "Multi-User Chat" command access level
to 1000, so only the SysOp can access it.
(c) Change the MAIN MENU "DOS hook 1" or "DOS hook 2" command
letter to "T".
(d) Change the MAIN MENU "DOS hook 1" or "DOS hook 2" command
access level to a level so that users can access it.
(e) Change the MAIN MENU "DOS hook 1" or "DOS hook 2" command
description to "[T]..Talk with other Node(s)" or something
like that.
(f) Go to the DOOR DEFINITION area of MAKEWILD, and change the
"DOS hook 1" or "DOS hook 2" multi-user flag to YES.
10. Use the WCTEXT.DAT editor to change the following prompts...
NOTE: Prompt numbers are for WildCat 3.5 beta.
#252 from @SUB@ is PAGING.
change the above prompts to...
#252 is PAGING you from WildChat.
11. Load one node of WildCat and give WildChat a try in local mode.
If there's any problem, review the setup for any mistakes, and
if the problem cannot be resolved, contact me through The Source
BBS.
WildChat(tm) Files <-- MUST, MUST, MUST READ!
══════════════════
WildChat(tm) uses several data files, this is an explanation of what they
are and how to maintain them.
Files that WildChat(tm) reads
─────────────────────────────
WILDCHAT.CFG The main configuration file
WILDCHAT.BAD The words for the language filter
WILDCHAT.LST The action commands
WILDCHAT.DAT The prompts and text
CFGHELP.BBS User Configuration help screen
MAINHELP.BBS Main Commands help screen
DOOR.SYS User Info created by WildCat!
o WILDCHAT.CFG is a cr/lf format text file. Use any text editor
to edit. If any lines are removed, the door will not run, and
possible will crash and do unpredictable things. Please, be
very careful with this file. Instructions on which lines are
which are in the file.
This is found in the WildCat root directory, which is pointed to
using the WCHOME environment variable.
o WILDCHAT.BAD is a cr/lf format text file. Put each word on a
separate line. If more than one word is placed on one line, then
the result may be unpredictable.
This file is found in the WILDCHAT directory.
o WILDCHAT.LST is a cr/lf format text file. Each action command
consists of three lines.
Line #1: COMMAND WORD
Line #2: TEXT IF COMMAND WORD IS TYPED ALONE
Line #3: TEXT IF COMMAND WORD IS TYPED WITH AN ADDRESSEE
Here's an example...
Line #1: LAUGH
Line #2: is laughing out loud!
Line #3: is laughing at @SUB@!
The code @SUB@ is used to insert the user-ID of the addressee.
This file is found in the WILDCHAT directory.
o WILDCHAT.DAT is the file containing the text that WildChat(tm)
outputs. This is the same format as WCTEXT.DAT, and can be edited
with the WCTEXT.DAT editor that is included with WildCat! Make
sure to make a backup before altering this file.
This file is found in the WILDCHAT directory.
o CFGHELP.BBS is a help screen in WildCat 3.0 format. You can use
@CLS@, @PAUSE@, and @xx@ color commands.
o MAINHELP.BBS is a help screen in WildCat 3.0 format. You can use
@CLS@, @PAUSE@, and @xx@ color commands.
o DOOR.SYS... read the WildCat! manual.
Files that WildChat(tm) creates
───────────────────────────────
WILDCHAT.DTA Contains node information (Who's Online, etc)*
WILDCHAT.MSG Contains messages that users type*
WILDCHAT.USR Contains user profiles and configuration
WILDLOG!.??? Contains logging information. Where ??? is the node #.
* denotes that file is a fixed size
o WILDCHAT.DTA contains information about who is inside WildChat(tm).
This file should be deleted on every boot-up (if not on a ram disk)
or any time that WILDCHAT.CFG changes.
This file is on the RAMDISK.
----> MAKE SURE ALL NODES ARE DOWN BEFORE DELETING OR EDITING ANY
WILDCHAT(tm) FILES!
----> IF YOU ARE GETTING A "NODE HANDLE IN USE" ERRORS THEN YOU MUST
----> DELETE WILDCHAT.DTA AND WILDCHAT.MSG.
o WILDCHAT.MSG contains the messages that the users type
to each other. This should be treated EXACTLY the way
WILDCHAT.DTA is treated.
This file is on the RAMDISK.
o WILDCHAT.USR contains user information and configuration. This
file can be deleted, but then users will have to log on new again,
which is not much of a hassle. (It may only confuse some users)
This file is found in the WILDCHAT directory.
o WILDLOG!.??? contains logging information for each node.
This file should be deleted whenever it gets too large.
These files are found in the WILDCHAT directory.
Special Thanks
══════════════
I'd like to thank the following people for making WildChat possible...
Michael Conley, thanks for all the suggestions, you were a big help!
Tom Tcimpidas, thanks for picking out all the minute details!
Chip North, thanks for running The Source, and for helping me test
this thing!
Jeff Sumberg, who wrote QBSerial, the serial communications
interface used in WildChat(tm). Thanks Jeff! You
wrote some GREAT routines!
Lance Stewart, beta tester.
Hugh Mitchell, beta tester.
Clayton Manson, beta tester.
Dan Stasinski, honorable mention. Good guy, great programmer, but
I still can't spell his name right.